COMMENT ⊗   VALID 00003 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	.<<     TWO COLUMN FORMAT       by L. Earnest           February 1975
C00007 00003	.<<Dec. '74	PUB Macro for AI Memo Cover and Title Pages	by LES
C00012 ENDMK
C⊗;
.<<     TWO COLUMN FORMAT       by L. Earnest           February 1975
.
.This is a description of how to use the PUB macros in BASKER.PUB[SUB,SYS].
.These macros set up one- or two-column formats with Section, Subsection, and
.Subsubsection numbering and automatic Table of Contents generation.
.
.                       Heading
.First, your file should specify the device.  If it is "DEVICE XGP", then
.you must specify of both a Font 1, which should be lightface,
.and Font 3, which should be boldface.  For example, if you say
. REQUIRE "BASKER.PUB[SUB,SYS]" SOURCE_FILE;
.you will get the three Baskerville fonts, with Font 2 being italic.
.
.                       One-sided Documents
.For documents that will be printed on only one side of the paper, the
.Section name will appear in the top left of each page and the page number
.in the top right.
.
.                       Two-sided Documents
.For documents that will be printed on both sides of the paper, even numbered
.(left) pages will have the page number in the upper left corner, followed by the
.the Section name.  Odd numbered (right) pages will have the Subsection name
.(if any) in the top left and the page number in top right.
.
.After the font specification, you specify one or two sides by including one
.of the assignments "SIDES←1;" or "SIDES←2;", followed by
. REQUIRE "TWOCOL.PUB[SUB,SYS]" SOURCE_FILE;
.If you neglect to specify the number of sides before the REQUIRE statement,
.PUB will complain about SIDES being undefined.
.
.                       Table of Contents
.If you wish to have a Table of Contents, put the PUB statement
. INSERT CONTENTS;
.at the place where you want them to appear, and call the macro
. BACK;
.at the very end of your document.
.
.                       Sections
.Begin each segment with the appropriate one of the following macros
.S <section name>
.SS <subsection name>
.SSS <subsubsection name>
.APP <appendix name>
.If the name is more than one line long, enclose it in vertical bars ("|").
.The subsections and subsubsections will be numbered decimally within
.the section and will appear in the Table of Contents.
.
.If you wish to use a subtitle in the text but you do not want it to
.appear in the Table of Contents, you can use the following macro to
.make it centered in boldface:
. CB <subtitle>
.
.Another handy macro is FAC which has been defined as "FILL ADJUST COMPACT",
.(i.e. normal justify mode).
.
.The macro ONECOL changes to a one column format (full width) and starts
.a new page, while TWOCOL goes back to the two column format, also on a new
.page.
.
.Let me know if something doesn't work.  (I won't guarantee
.to fix it, but I may offer interest and sympathy).
.                                                       LES
.>>
.<<Dec. '74	PUB Macro for AI Memo Cover and Title Pages	by LES
.
.This is a description of COVER.PUB[SUB,SYS], which
.contains a macro for making the cover and title
.pages of A. I. Memos.  In most cases it can be used "as is",
.else you can copy and modify it for unusual situations.
.
.The general form of the macro call is:
.  macro cover(aimno,csno,titl,auth,spons1,spons2,moyear,special,nack);
.where	aimno  = A. I. Memo #,
.	csno   = CS Report #,
.	titl   = title of the memo,
.	auth   = name(s) of author(s),
.	spons1 = first sponsor (if any),
.	spons2 = 2nd sponsor (if any),
.	spons3 = 3rd sponsor (if any),
.	moyear = month and year of publication,
.	special= special footnote (for title page),
.	nack   = anything here causes standard acknowledgement footnote
.		 to be suppressed.
.Any or all of the last four parameters may be omitted.  If the
.date is omitted, the current month and year will automatically
.be used.  You may insert a "↓" in either the title or list of
.authors wherever you wish them broken over two or more lines.
.The current list of sponsors known to this routine is ARPA,
.NASA, and NIMH.
.
.For example, if you PUB a file containing the following,
.  require "cover.pub[sub,sys]" source;
.  cover("254","74-472",|Stanford Automatic Photogrammetry Research|,
.    "Lynn H. Quam↓Marsha Jo Hannah");
.  <text of abstract>
.then the the top lines of both the cover and title pages will
.look like this (but wihout the dots in column 1):
......................................................................
.Stanford Artificial Intelligence Laboratory		 November 1974
.Memo AIM-254
.
.Computer Science Department
.Report No. STAN-CS-74-472
.
.
.		Stanford Automatic Photogrammetry Research
.
.				  by
.
.			     Lynn H. Quam
.			   Marsha Jo Hannah
.
......................................................................
.
.In this case, there will be no organizational acknowledgement and the
.text of the abstract will be put out in Baskerville 30 font.
.
.Alternatively, if the following call is used,
.  cover("254","74-472",|Stanford Automatic Photogrammetry Research|,
.    "Lynn H. Quam↓and↓Marsha Jo Hannah",NASA);
.then the word "and" will be inserted between the authors' names and
.acknowledgement of NASA support will be placed on both the front
.cover and in a footnote on the title page.
.
.Still another form is illustrated by
.  require "cover.pub[sub,sys]" source;
.  font A "sign57"; turn on "%";
.  cover("2954","86-1672",|%AFINAL REPORT↓%*Contraceptive Devices for Robots|,
.    "Virgina Reddy and Rod Supple",ARPA,"Zero Population Growth",May 1986);
.  font B "ngr 30"; select B;
.  <text of abstract>.
.Here, the title line is broken in two, with the first line in large
.type, and the authors are listed on one line.  Acknowledgements are
.generated for both ARPA and ZPG, a non-current date is used, and
.the abstract is printed in NGR30 rather than Baskerville.
.>>